home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.lang.c++
- Subject: Re: VC++ portable to Borland C++??
- Date: 20 Jan 1996 00:59:25 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4dpepd$fcs@news1.usa.pipeline.com>
- NNTP-Posting-Host: pipe7.h1.usa.pipeline.com
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Jan 19, 1996 16:19:40 in article <VC++ portable to Borland C++??>,
- 'cm2bcjr1@bs47c.staffs.ac.uk (cm2bcjr1)' wrote:
-
-
- >Hello
- >
- >I am having trouble linking a MSVC++ program with a Borland compiler.
- >I am using Borland C/C++ ver 3.1. and I think the VC is version 2.0.
- >The program compiles fine but it blows up when I link it. I've set
- Borlands
-
- What does 'blows up' mean? Undefined symbols? If so, what are
- some of the symbol names?
-
- >library and include directories to reference all VCs equivalent
- directories.
- >I get the feeling that Microsoft and Borland don't make portability easy
- >between the two compilers because of their rivalry. Has anybody else
- >experienced portability problems between the two??
- >
- A bigger issue is that one is a 16-bit compiler while the other is
- 32-bit. Writing and testing code on a 32-bit system then porting
- to a 16-bit one is asking for trouble, even if you get them to
- compile and link.
-
- --
- Pete Grant
- Kalevi, Inc.
- Object Oriented Software Development
-